-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: get rid of managedResource
#3297
refactor: get rid of managedResource
#3297
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably also wanna update the SQL schema: extensions/control-plane/store/sql/transfer-process-store-sql/docs/schema.sql#L68
1140c50
to
6c4c12d
Compare
6c4c12d
to
ab3c3dc
Compare
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #3297 +/- ##
===========================================
- Coverage 72.20% 17.74% -54.46%
===========================================
Files 837 837
Lines 16867 16832 -35
Branches 951 948 -3
===========================================
- Hits 12178 2987 -9191
- Misses 4296 13767 +9471
+ Partials 393 78 -315
☔ View full report in Codecov by Sentry. |
146dca0
to
e23f408
Compare
* refactor: get rid of managedResource * PR remarks * new dependencies file
What this PR changes/adds
removed the
managedResource
field onDataRequest
and all the accessors because it had no more meaning in the current situationWhy it does that
refactoring
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #3292
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.